Aggregated space system network

ABSTRACT

A system for aggregating spaced related systems includes accessing service provider information for multiple service providers to determine relevant services/systems available, automatically determining that no single service provider provides services sufficient to perform a particular space activity, automatically identifying multiple services from different service providers that in aggregate include performing the space activity, and automatically determining a parameter to configure space equipment to perform each of the multiple services from the different service providers in order to perform the space activity. In some embodiments, this system can be scaled across multiple regions (e.g., multiple planetary regions). For example, each region can have its own set of servers and ledgers that provide real-time services within the region and opportunistically synchronize between regions (e.g., when communication is available).

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional PatentApplication No. 62/984,942, “Aggregated Space System Network,” filed onMar. 4, 2020, which is hereby incorporated by reference in its entirety.

BACKGROUND

The number of space activities and the number of entities performingspace activities has been increasing. For purposes of this document,space activities are functions performed in space. The term “space”refers to being beyond the Earth's atmosphere, in orbit around theEarth, or at a distance from the Earth's surface that is equivalent to(or greater than) a distance of an object in orbit around the Earth.Examples of space activities include communication, transport, solarsystem exploration and scientific research. For example, theInternational Space Station is an orbiting research facility thatfunctions to perform world-class science and research that only amicrogravity environment can provide. Other activities performed inspace can also be considered space activities.

Often, a single entity performing a space activity will develop andimplement the entire system needed to perform the space activity. Forexample, one entity may build a constellation of satellites and aplurality of ground terminals to implement a communication system. Asspace activities become more complex, it is becoming too expensive,risky and complicated for one entity to develop an entire system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of one embodiment of a space system thataggregates multiple systems/services to perform a space activity.

FIG. 2 is a block diagram of one embodiment of an aggregation server.

FIG. 3 is a block diagram describing one embodiment for implementing apolicy manager of the aggregation server.

FIG. 4 depicts four domains and an example of implementing a policy.

FIG. 5 is a block diagram of an example architecture for one embodimentof the resource controller's data analytics pipeline.

FIG. 6 is a block diagram of an example architecture for one embodimentof the resource controller performing microservices.

FIG. 7 is a flow chart describing one embodiment of a process foroperating the system of FIG. 1.

FIG. 8 is a flow chart describing one embodiment of a process foroperating the system of FIG. 1.

FIG. 9 is a flow chart describing one embodiment of a process foroperating the system of FIG. 1.

FIG. 10 is a block diagram of one embodiment of a space system thataggregates multiple systems/services to perform a space activity.

FIG. 11 is a flow chart describing one embodiment of a process foroperating the system of FIG. 10.

DETAILED DESCRIPTION

To reduce costs, risks and complications of deploying large scalesystems for performing space activities, a lead entity (a client) canaggregate systems/services from multiple providers to support the spaceactivity (the mission). For example, a client can use a spacecraft froma first service provider for transport to/from a location in space; aspaced-based relay station from a second provider for communicationbetween Earth and the location in space; and one or more satellites froma third provider for communication between the relay station of thesecond provider and ground based terminals, all in support of a spaceactivity such as exploration of a planet, asteroid or moon. However,most spaced related service providers (operators of equipment thatperform services in space or in support of activities in space) providestand-alone solutions with no interoperability, ground and spacenetworks often have separate infrastructures with no shared resources,and it has been historically difficult for spaced related serviceproviders to work together to provide end-to-end solutions.

To enable aggregation of spaced related systems/services, an aggregationsystem is implemented electronically (e.g., one or more computer serversand, optionally, one or more wired/wireless networks), that allowsclients to obtain end-to-end spaced related systems/services in supportof a space activity. To successfully implement such a system, varioustechnical problems must be overcome. First, the servers need to identifyinteroperable services, including determining which space relatedsystems/services from which providers can work together to achieve themission. This may involve automatic translation of technical performancespecifications between different performance metrics, automaticdetermining of link budgets to verify that communication is possible,and/or automatic configuring of space and/or ground equipment to use theaggregated systems/services to perform the space activity. Second, theservers need to provide appropriate security, while balancingtransparency. For example, to record information about the aggregationof systems/services, ledgers can be used that are secure, distributedand immutable. Additionally, clients can specify security policiesregarding how services are performed, including whether thesystems/services should be public or hidden. Third, the space systemsneed should be fault tolerant. For example, the proposed aggregationsystem can be configured to automatically monitor the space activity,including the various system/services used to perform the spaceactivity, in order to identify faults or other issues. Some embodimentscan include automatically reconfiguring the space and/or groundequipment to use the aggregated systems/services differently in order toperform the space activity in light of the detected fault orreconfiguring the space and/or ground equipment to use different spacebased systems/services in order to perform the space activity.

One embodiment of the system described herein includes one or moreservers performing a machine implemented method comprising receiving arequest regarding performance of a space activity; accessing serviceprovider information for multiple service providers to determinerelevant systems/services available, automatically determining that nosingle service provider provides systems/services sufficient to performthe space activity, automatically identifying multiple systems/servicesfrom different service providers that in aggregate include performingthe space activity, and automatically determining a parameter toconfigure space equipment to perform each of the multiple services(and/or interact with the systems) from the different service providersin order to perform the space activity.

In one example implementation, the request identifies a first quantityfor a first performance metric and the automatically identifyingmultiple services from different service providers that in aggregateinclude performing the space activity includes: automaticallyidentifying a first space service that specifies a second quantity for asecond performance metric that is different than the first performancemetric and automatically translating between the first performancemetric and the second performance metric to determine whether the secondquantity for the second performance metric satisfies the first quantityfor the first performance metric; and the automatically determining theparameter includes automatically determining the parameter to configurespace equipment to perform the space activity using the first spaceservice such that the first quantity for the first performance metric issatisfied.

These systems described herein can be scaled across multiple regions(e.g., multiple planetary regions). For example, each region can haveits own set of servers and ledgers that provide real-time serviceswithin the region and opportunistically synchronize between regions(e.g., when communication is available).

FIG. 1 is a block diagram of a space system that aggregates multiplesystems/services to perform a space activity. That is, FIG. 1 shows aplurality of interoperable space assets from multiple service providers.In the example of FIG. 1, four separate service providers are depicted;however, more or less than four service providers can also be used. Inthis example, service provider 1 (SP1) includes a ground network 110that may comprise computers, mobile telephones, wired networks, wirelessnetworks, ground based satellite terminals, smart appliances, etc.,including a server 111 that stores a copy of a ledger L (more detailsabout the ledger are set for the below). Service provider 1 includes twosatellites 114 and 115, which may be any type of satellite or spacecraft(e.g., communication satellites, imaging satellites, satellites withsensors, etc.). In one embodiment, satellites 114 and 115 are ingeosynchronous orbit; however, other orbits can also be used. The groundnetwork 110 for service provider 1 communicates with satellites 114 and115 via one or more gateway terminals 112 (or other types of groundbased satellite terminals). Gateway terminals 112 communicate withsatellite 114 via wireless (e.g., RF or optical) communication link 116.Gateway terminals 112 communicate with satellite 115 via wireless (e.g.,RF or optical) communication link 117. In one embodiment, satellite 114communicates with satellite 115 via wireless (e.g., optical)communication link 118. Wireless communication links 116, 117 and 118are depicted as dashed lines to indicate that they are all part of asystem/service from service provider 1.

Service provider 2 (SP2) includes a ground network 120 that may comprisecomputers, mobile telephones, wired networks, wireless networks, groundbased satellite terminals, smart appliances, etc., including a server121 that stores a copy of ledger L. In this example, service provider 2provides space related ground-based equipment and services, but nosatellite or other airborne craft.

Service provider 3 (SP3) includes a ground network 130 that may comprisecomputers, mobile telephones, wired networks, wireless networks, groundbased satellite terminals, smart appliances, etc., including a server131 that stores a copy of ledger L. Service provider 3 includes twosatellites 134 and 135, which may be any type of satellite or spacecraft(e.g., communication satellites, imaging satellites, satellites withsensors, etc.). In one embodiment, satellites 134 and 135 are in lowearth orbit; however, other orbits can also be used. The ground network130 for service provider 3 communicates with satellites 134 and 135 viaone or more gateway terminals 132 (or other types of ground basedsatellite terminals). Gateway terminals 132 communicate with satellite134 via wireless (e.g., RF or optical) communication link 136. Gatewayterminals 132 communicate with satellite 135 via wireless (e.g., RF oroptical) communication link 137. In one embodiment, satellite 134communicates with satellite 135 via wireless (e.g., optical)communication link 138. Wireless communication links 136, 137 and 318are depicted as dotted lines to indicate that they are all part of asystem/service from service provider 3.

Service provider 4 (SP4) includes a ground network 140 that may comprisecomputers, mobile telephones, wired networks, wireless networks, groundbased satellite terminals, smart appliances, etc., including a server141 that stores a copy of ledger L. In some embodiments, a copy of theledger L will only be maintained by a subset of service providers or byone or more third parties (in addition to or in lieu of all or a subsetof service providers). Service provider 4 includes one relay station 146for relaying communication between Earth and a distant planet, moon, orregion of the solar system (see communications link 166). In oneembodiment, relay station 146 is further from the Earth's surface thengeosynchronous orbit. In some embodiments, relay station 146 is notorbiting the Earth and is outside the Earth's atmosphere (and/or outsidethe Earth's gravitational pull). The ground network 140 for serviceprovider 4 communicates with relay station 146 via one or more gatewayterminals 142 (or other types of ground based satellite terminals).Gateway terminals 142 communicate with relay station 146 via wireless(e.g., RF or optical) communication link 145.

FIG. 1 shows aggregation server 100 in communication with ground network110, ground network 120, ground network 130 and ground network 140. Inone embodiment, aggregation server 100 comprises one or more computersthat is/are programmed by software to perform the processes describedherein. For example, aggregation server 100 includes one or moreprocessors connected to a non-transitory computer readable storagemedium storing software code which when executing on the one or moreprocessors performs the processes described herein. Examples of thenon-transitory computer readable storage medium includes a solid statedrive, a hard disk drive, DRAM. SRAM, flash memory, a CDROM, etc. Theone or more processors are also connected to communication interfacesfor wired and wireless communication, as described herein. Examples ofcommunication interfaces includes an Ethernet interface, a WiFiinterface, Bluetooth interface, etc. As depicted in FIG. 1, andexplained in more detail below, aggregation server 100 maintains a copyof ledger L.

FIG. 1 shows client server 150 in communication with aggregation server100. Aggregation server 100 communicates with client server 150 andground networks 110/120/130/140 via public networks (e.g., the Internet)and/or private networks (e.g., private LAN, direct link or othernetwork/link). FIG. 1 depicts aggregation server 100 and ground networks111, 121, 131, and 141 positioned on (or near) the surface of the Earth,while satellites 114, 115, 134, 135 and 144 are in space.

An example entity wishing to perform a space activity uses client server150 to communicate with aggregation server 100 in order to aggregatespaced related systems/services. Many different space activities can beperformed, and can be used with the technology proposed herein. Oneexample is an entity exploring another planet, such as Jupiter. Theexample entity builds a spacecraft that travels to and subsequentlyorbits Jupiter for purposes of scientific research regarding Jupiter.However, the example entity does not have the infrastructure to performhigh speed communication between Jupiter and Earth, transmit thatcommunication to different regions of Earth that are far from each other(including different hemispheres), and manage the large amounts of datagenerated during the exploration of Jupiter. Therefore, the example,entity uses client server 150 to communicate with aggregation server 100in order to aggregate spaced related systems/services from multipleentities to perform the functions needed by the example entity.

Upon (and in response to) receiving the request from client server 150,aggregation server 100 accesses service provider information formultiple service providers (e.g., for SP1, SP2,SP3, SP4, etc.) todetermine relevant services/systems available. This service providerinformation can include an identification of each service provider, anindication of all services provided by each service provider, thetechnical specifications of all services provided by each serviceprovider, and cost information. The technical specifications can include(but is not limited to) location, bandwidth, power, modulation, coderate, etc. Based on the service provider information, for this example,aggregation server 100 automatically (e.g., without human intervention)determines that no single service provider (by itself) provides servicessufficient to perform all of the functions needed by the example entityso that the example entity can complete its exploration of Jupiter (thespace activity). Thus, aggregation server 100 automatically identifiesmultiple services from different service providers that in aggregateallow for the exploration of Jupiter by the example entity. For example,aggregation server 100 automatically identifies that service provider 4includes relay station 146 that can be used to communication betweenEarth and Jupiter via inter-planetary communications link 166.Aggregation server 100 also identifies that service provider 1 includessatellites 114 and 115 for transmitting communications to differentregions of Earth that are far from each other (including differenthemispheres) and service provider 3 includes satellites 134 and 135 fortransmitting communications to different regions of Earth that are farfrom each other (including different hemispheres). Depending on thecoverage areas of satellites 114/115 and satellites 134/135, aggregationserver 100 may choose either service provider 1 or service provider 3 toprovide the services of transmitting communications to different regionsof Earth. In one set of embodiments, aggregation server 100 may chooseboth service provider 1 and service provider 3 to meet bandwidth andlocation demands. Aggregation server 100 also identifies that serviceprovider 2 includes a ground network 120 that includes server farms forstoring data on behalf of the example entity and parallel processingcenters to process the data generated while exploring Jupiter andtransmitted to Earth via relay station 146 and stored in a server farmthat is part of ground network 120.

Aggregation server 100 combines the services from the different serviceproviders to create a larger system of space vehicles, computingdevices, communications equipment, etc. Aggregation server 100 verifiescompatibility between the various services. For example, aggregationserver 100 automatically determines one or more parameters to configurespace equipment and ground equipment to perform each of the multipleservices from the different service providers (without conflict betweenservices) in order to perform the space activity as a whole.

Aggregation server 100 also maintains ledger L as a series of recordsarranged as a block chain, where each record corresponds to atransaction and identifies a service provider, a service, a securitypolicy, a service level agreement and other contract terms. Copies ofledger L are also separately maintained at other servers. FIG. 1 showseach of the service providers maintaining a copy of ledger L; however,in other embodiments less than all service providers maintain a copy ofledger L. Alternatively (or in addition), copies of ledger L can bemaintained by computing systems that are not part of a service provider.

FIG. 2 is a block diagram that depicts more details of aggregationserver 100. In one embodiment, each of the components of aggregationserver 100 depicted in FIG. 2 comprise software/code that is stored on anon-transitory computer readable storage medium and, when executing onone or more processors of aggregation server 100, implements thefunctions described herein to perform the methods described herein. Thissoftware includes a resource controller 202, policy manager 204, ledger206, mission management interface 208, business support interface 210and communication manager 220 (including ground equipment interface 224and equipment interface 222). For example, resource controller codeimplements the resource controller 202, ground equipment interface codeimplements the ground equipment interface 224, space equipment interfacecode implements the space equipment interface 222, policy managementcode implements the policy manager 204, mission management interfacecode implements the mission management interface 208 and businesssupport interface code implements business support interface 210.

Resource controller 202 is the central processor that is responsible forcore operations of the aggregation server, including interfacing withservice providers (e.g., service provider 1, service provider 2, serviceprovider 3, . . . service provider N), figuring out what is availableand how to use it. Resource controller 202 is configured to receive arequest regarding performance of a space related activity, accessservice provider information for multiple service providers to determinerelevant services available, and identify one or more services from oneor more different service providers that in aggregate include performingthe space related activity. The resource controller will create andimplement interfaces between systems of different service providers, setup handovers between satellites of different providers, and ensure thatdesired performance metrics are met.

Policy manager 204 is in communication with resource controller 202 and,as will be described in more detail below, restricts services that canbe used by resource controller 202 (and other entities) based on sharingpolicies, usage policies and personnel policies (as well as other typesof policies).

Ledger 206 include a ledger in the form of a data structure and thesoftware to manage that ledger. In one embodiment, the ledger implementsblockchain technology and comprises a set of linked records. Each recordidentifies a transaction for a space system/service and contains a hashof a previous record to prevent records from being manipulated aftercommitting. Copies of the ledger are maintained at a set of servers inthe network so that a record is committed in the ledger only withvalidation from and storage in ledgers of other servers of the set ofservers in the network.

Communication manager 220 enables and manages communication betweenaggregation server 100 and the various service providers. In oneembodiment, communication manager comprises ground equipment interface224, which is in communication with the resource controller 202 andground equipment that may or may not communicate with equipment inspace. Communication manager 220 also includes space equipment interface222, which is in communication with resource controller 102 andequipment in space.

Mission management server 212 is an external computing device that isused to manage a space based mission. For example, a client mayimplement a mission management server 212 to manager that client's spaceactivity (e.g., exploration of Jupiter). Mission management interfacecode is in communication with resource controller 100 and externalmission manager server 212.

Business support server 214 is an external computing device that is usedto compute, track, store and report business analytics for one or moremissions. Business support interface 210 is in communication withresource controller 100 and business support server 212.

Aggregation server 100 electronically receives requests from clients(e.g., client A, client B, client C, client D, client E) to aggregatesystems/services from one or more service providers (e.g., serviceprovider 1, service provider 2, service provider 3, . . . serviceprovider N). Service provider 1 includes its own ground network 1,service provider 2 includes its own ground network 2, service provider 3includes its own ground network 3, and service provider N includes itsown ground network N. All of the ground networks 1-N are incommunication with aggregation server 100 via ground segment interface224 of communication manager 220.

Once aggregated, the aggregated systems/services can be utilized byusers (e.g., user group A, user group B, user group C, user group D anduser group E). In one embodiment, a user group is an aggregation ofassets under a single user authority with a single policy. The systemallows users to request services with ease, and permit the system toprovide high availability and robustness in a manner consistent withpolicy. The assets in a User Group are administrated through theaggregation server 100 and governed by rules originated from thisowner/authority with the priorities and rules managed by the policymanager 204 and contracted with each of the service providers that areproviding part/all of the services.

In one embodiment, user group A utilizes aggregated systems/servicesfrom one or more service providers in response to a request from clientA as part of performing a space activity, user group B utilizesaggregated systems/services from one or more service providers inresponse to a request from client B as part of performing a spaceactivity, user group C utilizes aggregated systems/services from one ormore service providers in response to a request from client C as part ofperforming a space activity, user group D utilizes aggregatedsystems/services from one or more service providers in response to arequest from client D as part of performing a space activity, and usergroup E utilizes aggregated systems/services from one or more serviceproviders in response to a request from client E as part of performing aspace activity.

FIG. 2 shows the stakeholders and the flow of agreements betweenorganizations facilitated by the resource controller 202 and policymanager 204. Each Policy Authority and the Service Providers, throughthe aggregation server 100, must agree on the policies pertaining tothat authority's User Group and assets. The Service Providers and UserGroups agree to policies which include classification, allowable UserGroup to Service Provider system connectivity, service priority,recovery priority, desired SLA terms, and which users are trusted forsharing. The policy manager 204 manages these policies and provides themto the resource controller 202, which pushes the appropriate policiesout to the service provider's systems including the space networks,ground networks, and terminals. The User Group issues credentials toemployees that use information, and the resource controller 202 is awareof cross-User Group credentials.

FIG. 3 shows an example of how a mission with security requirementscould be met for a single User Group connection and one for a cross UserGroup connection. Policy Manager 204 stores sharing policies 302, usagepolicies 304 and personnel policies 306. Other types of polices can alsobe stored and managed. Sharing policies 302 (in one embodiment providedby owners of information stored/managed by a system/service) identifyhow users of a system/service can share that system/service with otherusers outside their User Group. Usage policies 304 (in one embodimentprovided by owners of user assets that operate with a system/service)identify what actions can be taken by a user group with respect to asystem/service. Personnel policies 306 (in one embodiment provided byconsumer organizations) identify which users and/or user groups canaccess a system/service. For the users of the system, trust flows fromaccrediting organizations through stakeholders to principals who areexecuting missions. The stakeholders consists of the owners of theinformation, the owners of the assets, and the consuming organizationspersonnel. User Groups usually have their own terminals, personnel andpolicies. User Groups may accredit other User Groups that it is willingto share information with which means that the target organization hasbeen examined and determined trustworthy for connections, possibly withguards. Policy manager 204 manages these policies 302, 304, and 306 andprovide them to the resource controller 202. Resource controller 202aggregates and provisions systems/services in a manner that complieswith the policies 302, 304, and 306 provided by policy manager 204.

For example purposes, FIG. 3 shows two data sources 312 and 322, twonetworks 310 and 320, and two data sinks 314 and 324. More or less thantwo data sources, networks and data sinks can be implemented. The datasource 312 and the data sink 314 are owned or controlled by a singleentity associated with the single use group; therefore, in this examplethe policy governing use of the service provider network 310 and datasource 312 allows the single user group associated with the data sink314 full unrestricted access to the data from data source 312. At thesame time (e.g., simultaneously or at overlapping times) that the singleuser group associated with the data sink 314 has access to the data fromdata source 312 (via network 310), another user group associated withthe data sink 324 has some access the data from data source 322 (vianetwork 320). However, data source 322 is associated with a first usergroup and data sink 324 is associated with a second user group, thusconnection of the data sink 324 to data source 314 is a cross groupconnection that is governed by a policy managed by policy manger 204 andimplemented by resource controller 202. For example, FIG. 3 shows policyguards 330 implemented in the connection of the data sink 324 to datasource 314. Although policy guards 330 is depicted as a rectangle in theconnection, that depiction is symbolic as (in one embodiment) the policyguards 330 will be implemented by resource controller 202. Examples ofpolicy guards 330 include restriction on individuals who can accessinformation, time periods that the information can be accessed,geographic locations in which the information can be accessed, etc.

FIG. 4 depicts four domains and an example of implementing a policybetween users crossing multiple domains. FIG. 4 shows four domains (eachcomprising multiple computers/clients) including the Red Domain(comprising two separate locations 402 and 404), the Blue Domain 410(e.g., a Landlord Network), the Black Domain 412 (e.g., an ISP Network),and a Green Domain 414 (e.g., a Landlord Network). At the border betweendomains are guards G (also called gateways or routers), which managemessages passed between domains. As an example, a policy managed bypolicy manager 204 indicates that users in Red Domain 402 can set up aVirtual Private Network (“VPN”) to users in Red Domain 404. Resourcecontroller 202 will set up a secure communication link as a VPN 420 thattunnels through Blue Domain 410, Black Domain 412 and Green Domain 414(e.g., VPN 420 is established between Landlord Networks).

Policy manager 204 manages policy to define the level of trust betweenUser Groups. User Groups manage their own key material, and resourcecontroller 102 administers VPN tunnels to facilitate communicationbetween User Group guards. When providing connectivity between subnetsat the same classification, the gateway access points on the serviceprovider network must be known to the resource controller 102. Theestablished policy must allow the service provider's network to carrythe (possibly encrypted) User Group data, and the User Group mustprovide the keying material and form the VPN tunnels between the twousers. Alternatively, resource controller 102 may form a new informationdomain between the two guards with VPN tunnels forming in two stepsto-and-from the administrative domain.

To provide connectivity services between subnets at differentclassification, guards may be required at both ends. The access pointson the service provider's network must be known to the resourcecontroller 102 to facilitate the forming of guards, and when policyallows, the two information domain User Groups will have common keyingmaterial to allow the guards to form a VPN.

FIG. 5 is a block diagram of an example architecture for one embodimentof software components for resource controller 202. In one embodiment,resource controller 202 comprises a data preparation module 502 thatoperates on the following data sources: routing data 504, user activitydata 506, access event data 508, sensor data 510, satellite activitydata 512, ground activity data 514 and interface activity data 516. Datapreparation module 502 communicates data to data storage module 520 andperiodic data acquisition module 522 (which transmits information todata storage module 520). Real-time processing and transformation module524 is in communication with data storage module 520,Explore/Create/Train/Retrain/Validate Models module 526, datamaterialization module 530 and custom applications 540. Datamaterialization module 530 sends output to data visualization module532, which outputs to custom applications 540.Explore/create/train/retrain/validate models module 526 provides modelsto model deployment model 528, which sends output to data storage module520 and custom applications 540. In one embodiment, custom applications540 includes business intelligence/dashboards/reports/predictionsapplications 542, alerts/notifications/rules driven actions applications544, and logic & machine driven recommendations/predictions/explorationapplications 546.

The software modules depicted in FIG. 5 (and executing on resourcecontroller 202) comprise a data analytics pipeline. Data ingestion isthe first tier in the data analytics pipeline and is the entry point forbringing data into the system. FIG. 5 depicts a subset of possible datasources (504-516) and the components to systematically store the bigdata into a distributed data store 520. Real-time processing andtransformation module 524 is used to process and transform raw data anda common query engine within data materialization module 530 provides ahigh level abstraction for querying data. The distributed event storeand messaging system is used for raw data aggregation and serves as avery reliable buffer between various stages in the pipeline.

The distributed event store and messaging system effectively decouplesproducers and consumers of data, and combined with reliability,security, and efficiency, makes it a great data transportation backbonefor stream processing and real-time applications. It's essentially ahigh throughput distributed system that meets the demands of big datathrough its ability to scale horizontally by adding more commodityservers. It has the flexibility to ingest data from any connected datasources. One method could be through native or REST producers thatprogrammatically push data to the distributed event store/messagingsystem and another is through built-in connectors that does itautomatically from various external sources such as MongoDB, FTP, etc.Combined with the distributed data stream processing framework, it canbe used to track data changes and take action on that data either inreal-time or in batches.

The distributed data stream processing framework enables scalable,high-throughput, and fault-tolerant stream processing of live datastreams. Data is ingested from the distributed event store/messagingsystem and can be transformed using complex algorithms like map, reduce,join, and window. Lastly, processed data is pushed out into thedistributed database 520.

The distributed database 520 offers superior scalability, and faulttolerance. It offers a robust and expressive interface for modeling andquerying data. This is where the common querying engine comes in andbrings the simplicity and power of a popular querying language like SQL.SQL is an ANSI/ISO standard language for working with data for not onlystoring, modifying, retrieving, but also for analyzing data. This commonquerying language also acts as the bridge between data stored in thedistributed database and external applications to analyze the data suchas a Business Intelligence software, etc.

The business intelligence tier (elements with red outline) of the dataanalytics pipeline depicted in FIG. 5 comprises data materializationmodule 530, data visualization module 532, and custom applications 540,including business intelligence/dashboards/reports/predictionsapplications 542 which performs extracting, analyzing, and distributingdata from the data store to support decision making. It is the firststep in the area of data science in which the system explores andattempts to find patterns on new data through rich visualizationcapabilities provided by the Business Intelligence (BI) softwareplatform. The BI tool primarily serves as the delivery mechanism of thequery that is generated by the data stored through the common queryingengine of data materialization module 530. This BI tier in the dataanalytics pipeline produces business dashboards and reports thattransform complex data into business insights. This discovery step helpsuncover insights that will become the precursor for smarter and rulesdriven automated actions made possible by next tier in the pipeline,Rule-based System.

Acquired actionable insights from the Business Intelligence tier canthen be programmed as rules with custom triggering codes. Theseprogrammed rules are essentially human-driven automations through dataanalytics as opposed to machine learning automation, achieved in thehighest tier. They are used for automated decisions and decision supportto allow immediate and adequate reaction to external forces madeavailable from data.

A rule-based system is implemented using data preparation module 502,data storage module 520, periodic data acquisition module 522, real-timeprocessing and transformation module 524, and custom applications 540(including alerts/notifications/rules driven actions applications 544).These components execute a set of instructions or function in responseto events or direct invocations. The aggregation server 100, through itsserverless architecture, facilitates this use case and provides datascientists with the greatest ease to compose functions to be triggeredby any programmable event.

The business intelligence platform of the data analytics pipelinedepicted in FIG. 5 has built-in predictive analytics functions such astrend line calculation using linear regression, among others. This usesa complex predictive analytics system that comes equipped as a subset ofthe machine learning arm of the aggregation server 100.

Machine learning explores the construction of algorithms that can learnfrom heuristics and make predictions from data. These kind of algorithmsare the next step in the strictly static programmed instructions fromthe previous analytics maturity tiers. It does it byexplore/create/train/retrain/validate models module 526 building a modelfrom large sized database of sample inputs (e.g., training a classifiermodel). Typical machine learning tasks are concept learning, advancedpredictive modeling, clustering, and finding useful patterns. Theultimate goal is to improve learning in such a way that it comesautomatic so that no human interactions are needed. The built/trainedmodel can be used by model deployment module 528 to classify and/oranalyze data from data storage 520. The results of model deploymentmodule 528 using the model on the data is provided to logic & machinedriven recommendations/predictions/exploration applications 546 in orderto predict performance, problems and/or faults.

The data analytics pipeline collects a wealth of data and producesactionable insights, predictions, and recommendations. In oneembodiment, application software in the aggregation server 100 is thevehicle to deliver these analytical outputs and business functionalityto the users through rich, interactive UIs and effective userexperiences. Example application software in the aggregation server 100performs both event-driven microservices and serverless architectures.The former is used primarily by software developers to build, run,deploy, and manage the suite of aggregation server 100 full featuredapplications and the latter is geared towards data analysts and datascientists to compose nested data centric functions that get triggeredby data changes or other events.

Microservices are an architectural pattern in which complex applicationsare composed of small, independent processes that communicate with eachother through language-agnostic APIs. To avoid interdependencies, eachmicroservice should have minimal interaction with other microservicesthat are part of the system. This gives the advantage of independentdevelopment, deployment, and scale to the microservices.

Microservices being handled by separate logical development streamsmakes it easier for a new developer to understand the functionality of aservice and ramp up to speed. This is especially useful in an agileenvironment where the developers can constantly change and there isminimal dependency on an individual/contractor. Code maintenance relatedtasks are simpler as smaller services are much more readable and easilytestable. The system should be contractor independent such that servicesare isolated from each other and from other contractors' services whichreduce coupling to development and deployment lifecycles. Theaggregation server 100 may have specific requirements which requirespecialized expertise that spans across multiple contractors. Thismicroservices model allows a client to efficiently outsource the work todifferent contractors per specialization. This would be very difficultin a monolithic system because of the interdependency of services. Themicroservices architecture is technology agnostic, as it eliminateslong-term commitment to a single technology stack. Every microservicecan be built on a separate technology stack and can be redesigned,replaced, or upgraded independently as they execute in isolation. Thismeans that every microservice can be built using a different (or thesame) programming language and use a different (or the same) type ofdata store which best suits the solution. For example, a logging servicecan use a slower and cheaper data store, whereas a real-time service canuse a faster and more performant data store. This decreases thedependency concerns compared to the monolithic designs and makesreplacing services much easier.

The microservices can be fault tolerant. Failure of a service will notimpact other parts of the system, which is essential for large,business-critical applications. The decomposed nature of the servicesalso helps with fault isolation and troubleshooting. With proper healthmonitoring systems in place, a failure of a microservice can be easilyidentified and rectified without causing downtime to the rest of theapplication. This also applies to application upgrades. If a newerversion of a service is not stable, it can be rolled back to an olderversion with minimal impact to the overall system. The microservicesshould be highly extensible. An event driven microservices architecturecan securely allow permissioned entities to tap into the flow andevent-based communication exchanges between services. This abilityempowers contractors to easily develop add-ons and new features on topof existing services without fear of impacting them. For instance, if anotification service is desired to email interested parties when anetwork failure occurs, the new service can simply subscribe to anetwork failure event already provided by an existing service andimplement the functionality from there. The ability of microservices tobe executed as an isolated process decouples it from the constraintsaround a specific hosting environment. For instance, services can bedeployed across multiple cloud providers and/or stacks and acrossdifferent operating systems. This decouples the technology limitationsfrom the business requirements. Each microservice can be separatelyversioned, upgraded, and scaled without impacting the rest of thesystem. This enables running multiple development streams in parallelwith independent delivery cycles aligned with the business demands.Microservices, being small and focused on a specific business scenario,improve the opportunity for them to be reused across multiplesubsystems. This will provide huge cost savings to the project.

FIG. 6 is a block diagram of an example software architecture for oneembodiment of components for the resource controller 202 that performmicroservices. Each of the components depicted in FIG. 6 are softwarethat programs one or more processor to perform the functions describedherein. The components of Microservices Architecture are divided into afront end 602, external set 604 and a microservices backend 606, thatwhen combined are used to implement Software as a Service (SaaS 608),Platform as a Service (PaaS 610) and Information as a Service (IaaS612).

Front end 602 includes real-time web applications 630, real-time desktopapplications 632 and real-time mobile applications 634, all of which aremicroservices application for a specific mission and provide outputs(e.g., via TCP) to a Distributed Ledger/Event Store/Message System 662of microservices backend 606. In one embodiment, microservices backend606 also includes real-time server 650, API gateway 652, statefulservice 654 (e.g., includes a data store), Stateless Services/ExternalAPI Wrappers 656, and webhook gateway 660. Real-time server 650 providesdata (e.g., via Websockets) to real-time web applications 630, real-timedesktop applications 632 and real-time mobile applications 634. APIgateway 652 provides data (e.g., via HTTPS) to real-time webapplications 630, real-time desktop applications 632 and real-timemobile applications 634. API gateway also communicates with statefulservice 654, Stateless Services/External API Wrappers 656, andDistributed Ledger/Event Store/Message System 662. The externalapplications 604 include internal plugins & app integrations 642 andexternal apps, plugins and app integrations 644, both of which are incommunication with API gateway 652 and Webhook gateway 660 (e.g., viaHTTPS).

The system can implement a serverless architecture, or Functions as aService (FaaS), which is similar to microservices architecture but itdecomposes services even further into many smaller functions. Moreimportantly, it abstracts away the service containerization processaltogether, so developers can quickly compose function level codes withany popular programming languages without having to think about thelogistics of serving the containers. The developed functions or actionscan be triggered through events that can come from the data store 520,real-time processing and transformation module 524 or other applicationsor sources. The serverless architecture supported by the aggregationserver 100 application logic that runs when an event occurs in responseto triggers (an event that triggers a certain action to execute). Rulesare associated with a trigger to an action. A rule defines what happenswhen a certain trigger occurs or is fired. An action can be defined in away such that it is a sequence of multiple actions.

FIG. 7 is a flow chart describing one embodiment of a machineimplemented (automatic) process for operating aggregation server 100 inthe system depicted in FIG. 1. In step 702, aggregation server 100receives a request regarding performance of a space activity. Therequest can be received via a message, an API, a user interface, etc.For example, the request may include an indication of a space activityto be performed and/or one or more indications of systems/servicesneeded for the space activity. In step 704, aggregation server 100accesses service provider information for multiple service providers todetermine relevant systems/services available. The service providerinformation includes identification of service providers, the systemseach service provider operates, the services available from the serviceprovider, performance metrics for each system or service, and operatingdetails for each system or service. In one embodiment, the serviceprovider information is stored in a data store at or in communicationwith aggregation server 100. In step 706, aggregation server 100 choosessystems/services from the service provider information that can be usedto perform the space activity in accordance with the request received instep 702. Aggregation server 100 provisions the chosen systems/serviceson behalf of the client submitting the request in step 702.

In step 708, aggregation server 100 determines one or more parameters toconfigure space equipment to perform the space activity. The one or moreparameters can include power, frequency, polarization, modulation rate,error code information, pointing angle, timing information, etc. For anexample where the provisioned system/service is a satellitecommunications link, step 708 may include activity determining a linkbudget for communication between a satellite and ground terminals, andthe above-listed parameters for the satellite and ground terminals tosuccessfully perform the communication. In step 710, aggregation server100 communicates with ground equipment, including using the one or moreparameters to configure the ground equipment to perform the spaceactivity using one or more of the provisioned system/services. In theabove example where the provisioned system/service is a satellitecommunications link, step 710 includes configuring the ground terminalsto successfully perform the communication using the above-listedparameters. In step 712, aggregation server 100 communicates with spacebased equipment, including using the one or more parameters to configurethe space based equipment to perform the space activity using one ormore of the provisioned systems/services. In the above example where theprovisioned system/service is a satellite communications link, step 712includes configuring the satellite(s) to successfully perform thecommunication using the above-listed parameters.

In step 714, aggregation server 100 implements a security policy for therequest. That security policy is managed by the policy manager 204 andimplemented by resource controller 202. For example, the requestreceived in step 702 may include information for a security policy(e.g., no operations may be performed in country X), and thatinformation is provided to policy manager 204. Alternatively, clientserver 150 may be used to communicate directly with policy manager 204to provide information (e.g., via an API, a message, etc.) regarding asecurity policy. In step 716, aggregation server 100 interfaces with amission manager server 212 (via mission management interface 208) inorder to report details of the provisioning and performance ofsystem/services and for receiving additional data or requests frommission manager server 212.

In step 718, aggregation server 100 monitors the multiplesystems/services identified and provisioned. For example, each of thesystems/services can report back status information to aggregationserver 100. Additionally, aggregation server 100 can actively obtainstatus information by using the systems/services, researchingenvironmental data (e.g., weather, war, natural disasters, etc.), orother means. In step 720, aggregation server 100 determines a faultcondition in a first system/service of the multiple system/services. Forexample, based on reporting or observing performance, aggregation server100 may determine that a communications link between a first satelliteand a region on the Earth is down. In step 722, aggregation server 100automatically identifies an alternative service to the first service.For example, after determining that the communications link between thefirst satellite and the region on the Earth is down, aggregation server100 automatically identifies a second satellite to provide thecommunications link for the Earth. In step 724, aggregation server 100automatically determines an update to the one or more parameters toreconfigure the ground equipment and/or the space equipment to performthe space activity using the alternative service in lieu of the firstservice, or determines an update to the one or more parameters toreconfigure the ground equipment and/or space equipment to perform thefirst service after the fault condition.

FIG. 8 is a flow chart describing one embodiment of a machineimplemented (automatic) process for operating aggregation server 100 inthe system depicted in FIG. 1. The process of FIG. 8 represents oneembodiment of an implementation of all or a portion of the process ofFIG. 7. In step 802, aggregation server 100 receives a request regardingperformance of a space activity. Step 802 corresponds to step 702 ofFIG. 7. In step 804, aggregation server 100 accesses service providerinformation for multiple service providers to determine relevantsystems/services available. Step 804 corresponds to step 704 of FIG. 7.In step 806, aggregation server 100 automatically determines that nosingle service provider provides services sufficient to perform thespace activity. For example, if the request of step 802 was forcommunication services from Earth to Jupiter, step 806 may includeaggregation server 100 determining that there is not already existing asingle system from a service provider that provides communicationservices from Earth to Jupiter. In step 808, aggregation server 100automatically identifies multiple services from different serviceproviders that in aggregate include performing the space activity. Thephrase “in aggregate include performing the space activity” is usedherein to mean that the combination of the system/services can be usedto perform the requested space activity as per the request of step 802.In the example where the request of step 802 was for communicationservices from Earth to Jupiter, and it was determined that there is notalready existing a single system that provides communication servicesfrom Earth to Jupiter, then step 808 may include identifying a firstsystem/service for communication between Earth and geosynchronous earthorbit, and a second system/service that includes a relay betweengeosynchronous earth orbit and Jupiter. Steps 806 and 808 correspond tostep 706 of FIG. 7. In step 810 of FIG. 8, aggregation server 100automatically determines one or more parameters to configure spaceequipment and ground equipment to perform each of the multiple servicesfrom the different service providers in order to perform the spaceactivity. Step 810 corresponds to step 708 of FIG. 7. In someembodiments, after step 810 is performed, aggregation server 100 canperform (all of or a subset of) steps 710-724.

FIG. 9 is a flow chart describing one embodiment of a machineimplemented (automatic) process for operating aggregation server 100 inthe system depicted in FIG. 1. The process of FIG. 9 represents oneembodiment of an implementation of all or a portion of the process ofFIG. 7. In step 902, aggregation server 100 receives a request regardingperformance of a space activity. The request identifies a first quantityfor a first performance metric for the space activity. In general, aperformance metric is defined as figures and data representative of asystem's actions, abilities, and overall quality. Examples ofperformance metrics include maximum power, minimum power, bandwidth,transmission speed, error rate, frequency range, etc. Step 902corresponds to step 702 of FIG. 7. In step 904, aggregation server 100identifies a first space system/service that specifies a second quantityfor a second performance metric. The second performance metric isdifferent than the first performance metric; therefore, aggregationserver 100 needs to determine whether the second quantity for the secondperformance metric is at least equivalent to (or better) than firstquantity for a first performance metric. In step 906, aggregation server100 translates between the first performance metric and the secondperformance metric to determine whether the second quantity for thesecond performance metric satisfies the first quantity for the firstperformance metric. Consider an example where the request received instep 902 includes a requirement that video files be transferred forstreaming from location A to location B at a predetermined quality. Inthis example, the first performance metric is video quality and thefirst quantity for the first performance metric is a particular videoquality level/magnitude. Examples of the first quantity for the firstperformance metric include 4K video, 1080P, etc. However, the serviceprovider who operates the satellite sells transponder bandwidth;therefore, the second performance metric is transponder bandwidth andthe second quantity is a measure of transponder bandwidth (e.g., for atransponder on the satellite). In this example, step 906 comprisestranslating the video quality requirements to transponder bandwidth toverify that the video quality requirements are met (ie first performancemetric is satisfied). In step 908, aggregation server 100 automaticallydetermines one or more parameters to configure space equipment toperform the space activity using the first space system/service suchthat the first quantity for the first performance metric is satisfied.In some embodiments, after step 908 is performed, aggregation server 100can perform (all of or a subset of) steps 710-724.

The technology described herein for aggregating systems/services isscalable across multiple regions that are remote from each other, forexample, regions associated with different planets or moons (or othercelestial objects). In some embodiments, each region will include itsown local network. For example, FIG. 10 is a block diagram of oneembodiment of a space system that aggregates multiple systems/servicesthat includes three networks 1002, 1004 and 1006 that are remote fromeach other. Network 1002 is in proximity to the Moon. Network 1004 is inproximity to the Earth. Network 1004 is in proximity to Mars. Each ofthe networks comprises a plurality of space vehicles and servers. Each(or a subset) of the servers include a copy of a distributed ledgerconfigured to store records. Each record identifies a transaction for aspace service and contain a hash of a previous record to prevent recordsfrom being manipulated after committing. A record is committed in therespective network only with validation from and storage in ledgers ofone or more other servers. In one embodiment, the ledgers implementblock chain technology.

Network 1002 includes space vehicles SV1A, SV1B and SV1C, which can besatellites, space stations, relay stations, space based laboratories,transportation crafts, weather stations, etc. No particular type ofspace vehicle is required. Space vehicles SV1A, SV1B and SV1C are all inorbit around the Moon. Each (or a subset) of the space vehicles includesa server with a copy of a ledger. For example, space vehicle SV1Bincludes server 1010 having a copy of distributed ledger L1 and spacevehicle SV1C includes server 1012 having a copy of distributed ledgerL1. Space vehicle SV1A includes an instance of an aggregation server100, identified in FIG. 10 as aggregation server 100′. In oneembodiment, aggregation server 100′ is the same structure and performsthe same functions as aggregation server 100 discussed above.Aggregation server 100′ includes a copy of distributed ledger L1.Aggregation server 100′ performs the functions discussed above (e.g.,see FIGS. 7-9) for network 1002. Space vehicle SV1A is in communicationwith space vehicle SV1B via proximity link 1014 (e.g., wireless RF oroptical signal) and in communication with space vehicle SV1C viaproximity link 1016.

Network 1004 includes space vehicles SV2A, SV2B and SV2C, which can besatellites, space stations, relay stations, space based laboratories,transportation crafts, weather stations, etc. No particular type ofspace vehicle is required. Space vehicles SV2A, SV2B and SV2C are all inorbit around the Earth. Each (or a subset) of the space vehiclesincludes a server with a copy of a ledger. For example, space vehicleSV2B includes server 1020 having a copy of distributed ledger L2 andspace vehicle SV2C includes server 1022 having a copy of distributedledger L2. Space vehicle SV2A includes an instance of an aggregationserver 100, identified in FIG. 10 as aggregation server 100″. In oneembodiment, aggregation server 100″ is the same structure and performsthe same functions as aggregation server 100 discussed above.Aggregation server 100″ includes a copy of distributed ledger L2.Aggregation server 100″ performs the functions discussed above (e.g.,see FIGS. 7-9) for network 1004. Space vehicle SV2A is in communicationwith space vehicle SV2B via proximity link 1024 (e.g., wireless RF oroptical signal) and in communication with space vehicle SV2C viaproximity link 1026. Network 1004 also includes a control center CCbased on the Earth's surface; however, the control center can also belocated in space. Space vehicle SV2B is in communication with controlcenter cc via proximity link 1028.

Space vehicle SV2A (including aggregation server 100″) is incommunication with the control center CC via trunk link 1058 (e.g., ahigh bandwidth wireless RF or optical communication link optimized forlong distance communication). Space vehicles SV1A and SV1C are also incommunication with the control center CC via trunk links 1060 and 1062.In one embodiment, control center CC is an operations center thatcontrols the various space vehicles and networks.

Network 1006 includes space vehicles SV3A, SV3B and SV3C, which can besatellites, space stations, relay stations, space based laboratories,transportation crafts, weather stations, etc. No particular type ofspace vehicle is required. Space vehicles SV3A, SV3B and SV3C are all inorbit around Mars. Each (or a subset) of the space vehicles includes aserver with a copy of a ledger. For example, space vehicle SV3B includesserver 1030 having a copy of distributed ledger L3 and space vehicleSV3C includes server 1032 having a copy of distributed ledger L3. Spacevehicle SV3A includes an instance of an aggregation server 100,identified in FIG. 10 as aggregation server 100′″. In one embodiment,aggregation server 100′″ is the same structure and performs the samefunctions as aggregation server 100 discussed above. Aggregation server100′″ includes a copy of distributed ledger L3. Aggregation server 100′″performs the functions discussed above (e.g., see FIGS. 7-9) for network1006. Space vehicle SV3A is in communication with space vehicle SV3B viaproximity link 1044 (e.g., wireless RF or optical signal) and incommunication with space vehicle SV3C via proximity link 1036. Spacevehicles SV3A and SV3B are in communication with the control center CCvia trunk links 1064 and 1066.

Because of the distance between networks and the orbiting of planets andmoons, some pairs of networks may be in intermittent communication witheach other while other pairs of networks are in full time communicationwith each other. For example, network 1004 is only in intermittentcommunication with network 1006 such that there are connection timeswhen network 1004 is in communication with network 1006 and there arequiet times when network 1004 is not in communication with network 1006.In the example topography of FIG. 10, connection times include thosetime when space vehicle SV2A is in communication with control center CCvia trunk line 1058 and space vehicle SV3A is in communication withcontrol center CC via trunk line 1064. During connections times whennetwork 1004 is in communication with network 1006, aggregation server100″ can synchronize with aggregation server 100′″ via control centerCC, where such synchronizing includes ledger L2 synchronizing withledger L3. During quiet times, no synchronization occurs.

In one embodiment, the ledgers of different networks will have a commonset of records that are stored in the ledgers of the different networksand the ledgers will have separate records that are stored in ledgers ofonly one (or a subset) of the networks. For example, a common set ofrecords have security that allows storage in the ledgers L2 of network1004 and ledgers L3 of network 1006. One or more separate sets ofrecords have security that allows storage in the ledgers L2 of network1004 and not in ledgers L3 of network 1006. One or more separate sets ofrecords have security that allows storage in the ledgers L3 of network1006 and not in ledgers L2 of network 1004. Ledgers L2 of network 1004synchronize the common set of records with ledgers L3 of network 1006during connection times (via a synchronization process betweenaggregation servers 100″ and 100′″ through control center CC) and do notsynchronize the common set of records with ledgers L3 of network 1006during quiet times.

FIG. 11 is a flow chart describing one embodiment of a machineimplemented (automatic) process for operating the system of FIG. 10. Instep 1102, an aggregation server (e.g., aggregation server 100′,100″ or100′″) for a first network (e.g., network 1002, 1004 or 1006) performs atransaction for the first network. For example, in response to a requestreceived from a client server, an aggregation server may provision asystem/service from a service provider for the client server. Step 1102can include performing all of part of the processes of FIGS. 7, 8 and/or9. One example transaction can include provisioning a satellitecommunication link. In step 1104, data for the transaction (referred toas transaction data) is added to a new record in a local ledger (e.g.,L1, L2 or L3) for the first network. In step 1106, the aggregationserver for the first network adds a hash of a previous record to the newrecord in the local ledger. In step 1108, this newly created record issent to the ledgers at other servers in the same network. For example,if the first network of FIG. 11 corresponds to network 1004 of FIG. 10,then step 1108 includes aggregation server 100′″ sending a copy of thenewly created record to server 1030 for storage in its copy of ledger L3and to server 1032 for storage in its copy of ledger L3. Once each ofthe other servers store the new records and confirm authenticity, thenthe other servers send a validation of the record back to theaggregation server. Thus, in step 1110, the aggregation server for thefirst network receives validation for the new record from the otherservers of the first network. In step 1112, in response to thevalidations for the new record from one or more of the other servers,the servers for the first network commit the new record at each copy ofthe ledger. Thus, the system stores in the ledgers of multiple serversmultiple copies of records for the multiple systems/services that inaggregate include performing the space activity. Steps 1102-1112 can beperformed by a network in a multi-network system such as depicted inFIG. 10 and/or can be performed by a network in a single network systemsuch as depicted in FIG. 1. In step 1114, the ledgers of the firstnetwork (e.g., ledgers L3 of network 1004) synchronize records with theledgers of a second network (e.g., ledgers L2 of network 1002) duringconnection times and do not synchronize records with the ledgers of thesecond network during quiet times, as discussed above.

A system for aggregating spaced related systems has been described.

One embodiment includes a machine implemented method, comprising:receiving a request regarding performance of a space activity; accessingservice provider information for multiple service providers to determinerelevant services available; automatically determining that no singleservice provider provides services sufficient to perform the spaceactivity; automatically identifying multiple services from differentservice providers that in aggregate include performing the spaceactivity; and automatically determining a parameter to configure spaceequipment to perform each of the multiple services from the differentservice providers in order to perform the space activity.

One embodiment includes a non-transitory computer readable storagemedium storing software code which when executing on one or moreprocessors performs a method, the processor readable code comprisingresource controller code, ground equipment interface code, spaceequipment interface code, policy management code and mission managementinterface code. The resource controller code implements a resourcecontroller configured to: receive a request regarding performance of aspace related activity, access service provider information for multipleservice providers to determine relevant services available, determinethat no single service provider provides services sufficient to performthe space related activity, and identify multiple services fromdifferent service providers that in aggregate include performing thespace related activity. The ground equipment interface code implements aground equipment interface which is in communication with the resourcecontroller and ground equipment that communicates with equipment inspace. The space equipment interface code implements a space equipmentinterface that is in communication with the resource controller. Thepolicy management code implements a policy manager that is incommunication with the resource controller and space equipment. Thepolicy manager restricts services that can be used by the resourcecontroller based policy criteria. The mission management interface codeimplements a mission management interface which is in communication withthe resource controller and an external mission manager server.

One embodiment includes a machine implemented method comprising:receiving a request regarding performance of a space activity, therequest identifies a first quantity for a first performance metric forthe space activity; identifying a first space service that specifies asecond quantity for a second performance metric, the second performancemetric is different than the first performance metric; translatingbetween the first performance metric and the second performance metricto determine whether the second quantity for the second performancemetric satisfies the first quantity for the first performance metric;and automatically determining a parameter to configure space equipmentto perform the space activity using the first space service such thatthe first quantity for the first performance metric is satisfied.

One embodiment includes a first network in proximity to a first planetor moon, the first network comprises a first set of one or more spacevehicles and a first set of servers that each include a first ledger,each of the first ledgers of the first set of servers are configured tostore records that identify a transaction for a space service andcontain a hash of a previous record to prevent records from beingmanipulated after committing, a record is committed in the first networkonly with validation from and storage in first ledgers of multipleservers of the first set of servers; and a second network in proximityto a second planet or moon, the second network comprises a second set ofone or more space vehicles and a second set of servers that each includea second ledger, each second ledger of the second set of one or moreservers are configured to store records that identify a transaction fora space service and contain a hash of a previous record to preventrecords from being manipulated after committing, a record is committedin the second network only with validation from and storage in secondledgers of multiple servers of the second set of servers, the secondplanet or moon is remote from the first planet or moon, the secondnetwork is only in intermittent communication with the first networksuch that there are connection times when the second network is incommunication with the first network and there are quiet times whensecond network is not in communication with the first network, a commonset of records have security that allows storage in the first networkand the second network, one or more separate sets of records havesecurity that allows storage in the first network and not the secondnetwork, the second ledgers of the second network synchronize the commonset of records with the first ledgers of the first network duringconnection times and do not synchronize the common set of records withthe first ledgers of the first network during quiet times. In oneexample implementation, the first ledgers and the second ledgers areblockchains, and each transaction identifies a service, a securitypolicy, a service level agreement and another contract term.

One embodiment includes a processor connected to a storage device (e.g.,memory, hard disk drive, solid state drive, other type of flash memory)and a communication interface. The storage device (a non-transitorycomputer readable storage medium) stores code to program the processorto perform the methods described above.

For purposes of this document, it should be noted that the dimensions ofthe various features depicted in the figures may not necessarily bedrawn to scale.

For purposes of this document, reference in the specification to “anembodiment,” “one embodiment,” “some embodiments,” or “anotherembodiment” may be used to describe different embodiments or the sameembodiment.

For purposes of this document, a connection may be a direct connectionor an indirect connection (e.g., via one or more others parts). In somecases, when an element is referred to as being connected or coupled toanother element, the element may be directly connected to the otherelement or indirectly connected to the other element via interveningelements. When an element is referred to as being directly connected toanother element, then there are no intervening elements between theelement and the other element. Two devices are “in communication” ifthey are directly or indirectly connected so that they can communicateelectronic signals between them.

For purposes of this document, the term “based on” may be read as “basedat least in part on.”

For purposes of this document, without additional context, use ofnumerical terms such as a “first” object, a “second” object, and a“third” object may not imply an ordering of objects, but may instead beused for identification purposes to identify different objects.

For purposes of this document, the term “set” of objects may refer to a“set” of one or more of the objects.

The foregoing detailed description has been presented for purposes ofillustration and description. It is not intended to be exhaustive or tolimit the subject matter claimed herein to the precise form(s)disclosed. Many modifications and variations are possible in light ofthe above teachings. The described embodiments were chosen in order tobest explain the principles of the disclosed technology and itspractical application to thereby enable others skilled in the art tobest utilize the technology in various embodiments and with variousmodifications as are suited to the particular use contemplated. It isintended that the scope of be defined by the claims appended hereto.

What is claimed is:
 1. A machine implemented method for space systems,comprising: receiving a request regarding performance of a spaceactivity; accessing service provider information for multiple serviceproviders to determine relevant services available; identifying multipleservices from different service providers that in aggregate includeperforming the space activity; determining a parameter to configurespace equipment to perform at least one of the multiple services inorder to perform the space activity, the space activity is performed ina first network in proximity to a first planet or moon, the firstnetwork comprises a first set of one or more space vehicles and a firstset of servers that each include a first ledger, each of the firstledgers of the first set of servers are configured to store records thatidentify a transaction for a space service, the first network is remotefrom a second network, the second network is in proximity to a secondplanet or moon, the second network comprises a second set of one or morespace vehicles and a second set of servers that each include a secondledger, each second ledger of the second set of one or more servers areconfigured to store records that identify a transaction for a spaceservice; and storing in first ledgers of multiple servers of the firstset of servers copies of a first set of one or more records for at leasta subset of the multiple services that are included in performing thespace activity; and the first ledgers of the first network synchronizingthe first set of one or more records with the second ledgers of thesecond network.
 2. The machine implemented method of claim 1, whereinthe space equipment includes ground based equipment and space basedequipment, the method further comprising: communicating with the groundbased equipment; communicating with the space based equipment;implementing a security policy for the request; and interfacing with amission manager server.
 3. The machine implemented method of claim 1,wherein: the determining the parameter to configure space equipmentincludes using the parameter to configure the space equipment to performthe space activity using a first space service.
 4. The machineimplemented method of claim 1, wherein: the request identifies a firstquantity for a first performance metric; the identifying multipleservices from different service providers that in aggregate includeperforming the space activity includes: identifying a first spaceservice that specifies a second quantity for a second performance metricthat is different than the first performance metric, and translatingbetween the first performance metric and the second performance metricto determine whether the second quantity for the second performancemetric satisfies the first quantity for the first performance metric;and the determining the parameter includes automatically determining theparameter to configure space equipment to perform the space activityusing the first space service such that the first quantity for the firstperformance metric is satisfied.
 5. The machine implemented method ofclaim 4, wherein: the determining the parameter includes using theparameter to configure space equipment to perform the space activityusing the first space service such that the first quantity for the firstperformance metric is satisfied; and the method further comprisesmonitoring the first space service to verify that first quantity for thefirst performance metric is satisfied.
 6. The machine implemented methodof claim 1, wherein: the determining the parameter to configure spaceequipment comprises determining a link budget for communication betweenspace equipment.
 7. The machine implemented method of claim 1, furthercomprising: monitoring the multiple services; determining a faultcondition in a first service of the multiple services; automaticallyidentifying an alternative service to the first service; andautomatically determining an update to the parameter to reconfigure thespace equipment to perform the space activity using the alternativeservice in lieu of the first service.
 8. The machine implemented methodof claim 1, further comprising: monitoring the multiple services;determining a fault condition in a first service of the multipleservices; and automatically determining an update to the parameter toreconfigure the space equipment to perform the first service after thefault condition.
 9. The machine implemented method of claim 1, wherein:each of the first ledgers of the first set of servers are configured tostore records that identify a transaction for a space service andcontain a hash of a previous record to prevent records from beingmanipulated after committing, a record is committed in the first networkonly with validation from and storage in first ledgers of multipleservers of the first set of servers, each second ledger of the secondset of one or more servers are configured to store records that identifya transaction for a space service and contain a hash of a previousrecord to prevent records from being manipulated after committing, arecord is committed in the second network only with validation from andstorage in second ledgers of multiple servers of the second set ofservers, the second network is only in intermittent communication withthe first network such that there are connection times when the secondnetwork is in communication with the first network and there are quiettimes when second network is not in communication with the firstnetwork, a common set of records have security that allows storage inthe first network and the second network; and the first ledgers of thefirst network synchronize the first set of one or more records with thesecond ledgers of the second network during connection times and do notsynchronize the first set of one or more records with the second ledgersof the second network during quiet times.
 10. A machine implementedmethod for space systems, comprising: receiving a request regardingperformance of a space activity; accessing service provider informationfor multiple service providers to determine relevant services available;automatically determining that no single service provider providesservices sufficient to perform the space activity; automaticallyidentifying multiple services from different service providers that inaggregate include performing the space activity; automaticallydetermining a parameter to configure space equipment to perform themultiple services from the different service providers in order toperform the space activity, wherein the receiving a request anddetermining the parameter are performed in a first network in proximityto a first planet or moon, the first network comprises a first set ofone or more space vehicles and a first set of servers that each includea first ledger, each of the first ledgers of the first set of serversare configured to store records that identify a transaction for a spaceservice and contain a hash of a previous record to prevent records frombeing manipulated after committing, a record is committed in the firstnetwork only with validation from and storage in first ledgers ofmultiple servers of the first set of servers; and storing in firstledgers of multiple servers of the first set of servers multiple copiesof a first set of one or more records for the multiple services that inaggregate include performing the space activity.
 11. The machineimplemented method of claim 10, wherein the first ledgers areblockchains; and each transaction identifies a service, a securitypolicy, a service level agreement and another contract term.
 12. Themachine implemented method of claim 1, wherein: the space equipmentincludes a satellite and a ground terminal; the space activity includeswireless communication between the satellite and the ground terminal;and the determining a parameter includes determining at least oneparameter related to a link budget for the ground terminal.
 13. Themachine implemented method of claim 1, wherein: the second network isonly in intermittent communication with the first network such thatthere are connection times when the second network is in communicationwith the first network and there are quiet times when second network isnot in communication with the first network; and the first ledgers ofthe first network synchronizing the first set of one or more recordswith the second ledgers of the second network during connection timesand do not synchronize the first set of one or more records with thesecond ledgers of the second network during quiet times.
 14. A machineimplemented method comprising: receiving a request regarding performanceof a space activity, the request identifies a first quantity for a firstperformance metric for the space activity; identifying a first spaceservice that specifies a second quantity for a second performancemetric, the second performance metric is different than the firstperformance metric; translating between the first performance metric andthe second performance metric to determine whether the second quantityfor the second performance metric satisfies the first quantity for thefirst performance metric; and automatically determining a parameter toconfigure space equipment to perform the space activity using the firstspace service such that the first quantity for the first performancemetric is satisfied.
 15. The machine implemented method of claim 14,wherein: the automatically determining the parameter includes using theparameter to configure the space equipment to perform the space activityusing the first space service.
 16. The machine implemented method ofclaim 14, wherein: the automatically determining the parameter includesdetermining a link budget for communication between space equipment. 17.The machine implemented method of claim 14, further comprising:monitoring the first space service; determining a fault condition in thefirst space service; identifying a second space service that satisfiesthe first quantity for the first performance metric; and automaticallyupdating the parameter to reconfigure the space equipment to perform thespace activity using the second space service such that the firstquantity for the first performance metric is satisfied.
 18. The machineimplemented method of claim 14, further comprising: monitoring the spaceservice; determining a fault condition in the first space service; andautomatically updating the parameter to reconfigure the space equipmentto perform the space service after the fault condition such that thefirst quantity for the first performance metric is satisfied.
 19. Asystem comprising: a first network in proximity to a first planet ormoon, the first network comprises a first set of one or more spacevehicles and a first set of servers that each include a first ledger,each of the first ledgers of the first set of servers are configured tostore records that identify a transaction for a space service andcontain a hash of a previous record to prevent records from beingmanipulated after committing, a record is committed in the first networkonly with validation from and storage in first ledgers of multipleservers of the first set of servers; and a second network in proximityto a second planet or moon, the second network comprises a second set ofone or more space vehicles and a second set of servers that each includea second ledger, each second ledger of the second set of one or moreservers are configured to store records that identify a transaction fora space service and contain a hash of a previous record to preventrecords from being manipulated after committing, a record is committedin the second network only with validation from and storage in secondledgers of multiple servers of the second set of servers, the secondplanet or moon is remote from the first planet or moon, the secondnetwork is only in intermittent communication with the first networksuch that there are connection times when the second network is incommunication with the first network and there are quiet times whensecond network is not in communication with the first network, a commonset of records have security that allows storage in the first networkand the second network, one or more separate sets of records havesecurity that allows storage in the first network and not the secondnetwork, the second ledgers of the second network synchronize the commonset of records with the first ledgers of the first network duringconnection times and do not synchronize the common set of records withthe first ledgers of the first network during quiet times.
 20. Thesystem of claim 19, wherein: the first ledgers and the second ledgersare blockchains; and each transaction identifies a service, a securitypolicy, a service level agreement and another contract term.